-
Notifications
You must be signed in to change notification settings - Fork 139
feat(engine): actors lifecycle testing #3623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 11-10-chore_cleanup_rivet-engine_tests
Are you sure you want to change the base?
feat(engine): actors lifecycle testing #3623
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
More templates
@rivetkit/cloudflare-workers
@rivetkit/db
@rivetkit/framework-base
@rivetkit/next-js
@rivetkit/react
rivetkit
@rivetkit/sql-loader
@rivetkit/engine-runner
@rivetkit/engine-runner-protocol
commit: |
Pull Request Review: Rivet Actors Lifecycle TestingSummaryThis PR introduces a comprehensive Rust-based test runner infrastructure for deep actor lifecycle testing. It replaces the previous TypeScript-based test runner with a pure Rust implementation, enabling better control over actor behavior simulation and lifecycle scenarios. Changes: 21 files, +2813/-1059 lines ✅ Strengths1. Excellent Architecture
2. Comprehensive Test CoverageThe new tests cover critical lifecycle scenarios: actor creation, start timeouts, crash policies, graceful shutdown, input verification, and state transitions. 3. Better Test Reliability
|

No description provided.